Fix server column name in token entity unique constraint #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The generated name of the server column of
token_entity
isserver_uuid
, notserver
. The unique constraint on the table should reflect this.I ran into this problem when trying to create the necessary database tables for Autodone on a fresh PostgreSQL database. Hibernate tries to create the
token_entity
table using the following SQL:This obviously fails because the unique constraint refers to a column named
server
which doesn’t exist.